-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: ExMonobank.MerchantAPI #20
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job!
I have mixed fillings about Invoice module name, not clear that it is mutation DTO.
But I can live with it.
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big deal, just typo in file name:
cancel_invoice_failure_with_inbvalid_id.json
should be:
cancel_invoice_failure_with_invalid_id.json
fixture/vcr_cassettes/merchantapi/get_invoice_status_failure_with_inbvalid_id.json
Outdated
Show resolved
Hide resolved
Me too. We need clear separate request structs and response structs. I'm just bad at naming :) {:ok, invoice_info} =
%{amount: 100}
|> ExMonobank.Invoice.new()
|> MerchantAPI.create_invoice() I am open to any suggestions. |
@romkor I Just started extracting my code into ExMonobank.MerchantAPI. Work in progress, but we can start the discussion right now )